…rong results (#261)

Root cause: `schema-resolver.ts` passed flat schema_context
(`{"table": {"col": "TYPE"}}`) directly to `Schema.fromJson()`,
which expects the Rust `SchemaDefinition` format
(`{"tables": {"table": {"columns": [{"name": "col", "type": "TYPE"}]}}}`).
The parse silently failed, falling back to an empty schema, causing
all schema-dependent tools to produce empty/wrong results.

Fixes:
- `schema-resolver.ts`: Auto-detect and normalize 3 schema_context
  variants (flat map, array-of-columns, SchemaDefinition) before
  calling `Schema.fromJson()`
- `sql-analyze.ts`: Check `result.error` instead of `!result.success`
  to distinguish "issues found" from "analysis failed"
- `altimate-core-grade.ts`: Map Rust field names (`overall_grade`,
  `scores.overall`) instead of `grade`/`score`
- `altimate-core-complete.ts`: Use `data.items` (Rust field) with
  fallback to `data.suggestions`
- `altimate-core-schema-diff.ts`: Use `has_breaking_changes` (Rust)
  and format tagged enum changes correctly
- `altimate-core-rewrite.ts`: Use `data.suggestions` (Rust) with
  fallback to `data.rewrites`
- `altimate-core-fix.ts`: Map `fixes_applied`/`unfixable_errors`
  (Rust fields) instead of `changes`/`errors`
- `altimate-core-column-lineage.ts`: Show `column_dict` and use
  `lens_type` (Rust) for transform info
- `sql/register.ts`: Populate `can_auto_apply`, `original_fragment`,
  `rewritten_fragment` in `sql.rewrite` handler

Closes #261

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Full simulation of 77 tests across all altimate-core tools revealed
6 more field name mismatches between Rust napi output and TS formatters:

- `altimate_core.transpile`: QUALIFY post-processing checked `data.sql`
  but Rust returns `transpiled_sql` (array)
- `altimate_core.resolve_term`: Rust returns array, `toData()` converts
  to `{'0': ...}` object — now wraps as `{ matches: [...] }`
- `altimate_core_classify_pii`: checked `data.findings` but Rust returns
  `columns` with `classification`/`suggested_masking` fields
- `altimate_core_query_pii`: checked `data.exposures` but Rust returns
  `pii_columns` with `risk_level`/`suggested_alternatives`
- `altimate_core_testgen`: test cases have `inputs`/`expected` fields,
  not `sql` — formatter now shows input values and expectations
- `altimate_core_prune_schema`: checked `data.pruned` but Rust returns
  `pruned_schema_yaml`/`relevant_tables`/`tables_pruned`

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Stress simulation covering: SQL pattern variants (recursive CTEs,
LATERAL joins, GROUPING SETS), lint anti-pattern detection, column
lineage through 10 transformation types, schema diff mutation matrix
(100-column tables, special chars), 10-dialect transpile matrix,
grading consistency, fuzzy fix matching, testgen feature coverage,
cursor-position completions, PII detection, and term resolution.

Also fixes schema-resolver to skip tables with empty column lists
(Rust engine requires >= 1 column per table).

Total simulation suite: 288 tests, 867 assertions, 0 failures.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

1. `formatFix`: changed condition from `data.fixed && data.fixed_sql`
   to `data.fixed_sql && data.fixed !== false` so a valid `fixed_sql`
   is not silently discarded when `fixed` field is absent

2. `sql/register.ts`: wrapped all 10 composite SQL handlers in
   exportable `registerAllSql()` function (mirrors `registerAll()`
   pattern from `altimate-core.ts`)

3. All 3 e2e test files now call both `core.registerAll()` and
   `sql.registerAllSql()` in `beforeAll` to survive `Dispatcher.reset()`
   from other test files — fixes CI "No native handler" failures

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>